Described existing LTS updates as built-in into product #2752
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mnocon
commented
May 21, 2025
| composer require ibexa/product-catalog-date-time-attribute | ||
| ``` | ||
|
|
||
| ### Enable the bundle |
There was a problem hiding this comment.
This must be covered in the update doc - if someone didn't use LTS updates in v5, they must set them up when upgrading. Same for AI setup
ezrobot
requested review from
adriendupuis,
dabrt and
julitafalcondusza
and removed request for
a team
|
If you're in the middle of review, please note I've added an additional sentence: 50b9680 |
julitafalcondusza
requested changes
May 22, 2025
mnocon
commented
May 22, 2025
Co-authored-by: julitafalcondusza <[email protected]>
julitafalcondusza
approved these changes
May 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Target: 5.0 only - but the 5.0 mention in the homepage needs to be backported to other versions.
Open question:
What to do until the first LTS update after 5.0 is released? Do we keep separate versions of the home page for different versions, so that:
Description
#2751 should be merged first, as it defines the
latest_tag_5_0variable.Things done: